feat: lint the whole project using Super-Linter #544
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dunglas
force-pushed
the
feat/super-linter
branch
from
46f138a to
17c075f
Compare
dunglas
force-pushed
the
feat/super-linter
branch
from
17c075f to
034b4ff
Compare
dunglas
force-pushed
the
feat/super-linter
branch
from
034b4ff to
69fd710
Compare
dunglas
force-pushed
the
feat/super-linter
branch
from
a14cce1 to
f48c792
Compare
dunglas
force-pushed
the
feat/super-linter
branch
from
f48c792 to
92c8ef0
Compare
dunglas
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Super-Linter is a must-have; it automatically lints all files in the project, using popular linters.
It is especially useful to lint all the non-PHP files contained in a modern project:
Dockerfile, YAML, Kubernetes manifests, GitHub Actions...